Talk about the adaption of measuring CC so the number gives a better indication on actual complexity in the specific case of mapping code.\\

One of the returning patterns in mapping code that is perceived as not complex and easy to understand is the mapping of an optional field done as shown in Listing~\ref{optionalfieldmapping}.
The mapping of optional fields is counted for cyclomatic complexity as they consist of an if statement. Code as show in Listing~\ref{morecomplexcode} is perceived as more complex and harder to understand.
If cyclomatic complexity is used then there is no distinction between these cases. Two different pieces of code can have the same cyclomatic complexity, but one might contain more optional field mappings
than the other, resulting that the latter one is perceived as more complex.

To be able to differentiate better in mapping code the following change to cyclomatic complexity is proposed:
\begin{center}
Count cases as one would do with Cyclomatic Complexity, but do not count the cases that matches the rules that indicates it is an optional field mapping.
\end{center}
The metric will henceforth be referred to as \textit{Adjusted Cyclomatic Complexity}. If the following rules apply to an If Statement it is considered an optional field mapping pattern and it must not be counted for adjusted cyclomatic complexity:
\begin{enumerate}
	\item The boolean expression in the If Statement only contains one expression, so no infix expressions. (Validate terminology)
	\item The boolean expression is a method invocation and the final method called in the method starts with has
	\item The list of statements in the body of the If Statement contains only one statement
	\item The statement in the body is a method invocation with only one parameter
	\item The one parameter is a method invocation which is exactly the same as the method invocation in the boolean expression, except the final method call starts with get instead of has
\end{enumerate}
Listing \ref{exampleforrules} shows some examples of If Statements in regard to the above stated rules.
\input{sections/exampletorules.tex}

WORK QUESTION: Why is this change going to work?\\
The effect of not counting these cases for the cyclomatic complexity metric is that the number will be smaller because it does not contain the trivial cases that do not add to the complexity of understanding code.
\\\\
WORK QUESTION: What is the effect of the change?\\
The goal of the adaption is to be able to get better clues on what is complex code. Relate it to understanding code and maintainability, for example how much time one needs to under stand code. \\
Also explain what the measurement is not anymore. For example CC can be used for testing and calculation the amount of test cases. This is not possible anymore.
On what type of code does this change work?\\
Explain that it only works on mapping code within the System under Investigation. Might look at other pure JAXB based mapping code and check if the measurement still works.